Thanks for the PR!

• Contributor signed CLA now or in the past
  • If you just signed, leave a comment here with your real name
• PR's commit messages follow the commit message format

If you need to make changes to your pull request, you can update the commit with git commit --amend.
Then, update the pull request with git push -f.

Thanks again for your help!

Well done, and thank you. I agree that its not a problem to expressly flush the $timeout, but its something of a surprise unless you are aware that things like ngClass are animation-aware.

Ehm, I'm not sure what this means exactly. So now the animations (e.g. on ng-view) no longer run at the same time?

A problem I've been having with this, is that the leaving content on an ng-view gets cloned, but this means it loses it's scroll positions in all the content.

That way you see all content jump up just when the animation starts... Is this another issue? Then I'm sorry, I'll open another issue for that unless this PR fixes that.

@kevin-smets no this only means that if there is an animation already on a parent element then it won't asynchronously stop, but instead synchronously stop. It barely effects anything outside of tests and a bug with replace.

Your issue about content jumping most likely has to do with the DOM reordering. Please open a new issue with a plunkr example if possible.